Would love to hear some thoughts on this linter. In the interest of full disclosure, it was rejected by gocritic (see go-critic/go-critic#875). In practice, it has been immensely useful to my team. Thanks for your consideration. Details follow:

Makezero discourages the creation of slices with nonzero capacity but zero length. Its primary goal is to prevent appending to an initialized slice with nonzero length, but it can be used to disable uninitialized slices with nonzero length altogether. A common error among go programmers, particular when egged on by the useful prealloc linter, is this one:

x := make([]int, len(y))
for _, v := range y {
  x = append(x, v)
}

In this case, the programmer has forgotten to set the initial length of the array to 0 with make([]int, 0, len(y). In practice, my company has found it useful to any make calls with nonzero length, because the need to optimize by avoiding append statements is limited. We also like seeing append statements because they discourage the additional indirection introduced by indices needed to access elements in a preallocated non-zero length array (i.e. we don't see the index variable i all over the place like you'd see in C-language programs). We favorable readability of code over performance in almost all cases, adding nolint directives when we favor performance.

See https://github.com/ashanbrown/makezero for more details.